Summary of Changes

Hello @k13gomez, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical issue in the failsage library where asynchronous operations, particularly those subject to timeouts, were not reliably being canceled. The core problem stemmed from how AsyncExecution was handled, preventing proper interrupt propagation. The changes refactor the asynchronous execution logic to ensure that when a timeout occurs, the underlying futurama future is explicitly canceled and InterruptedException is correctly thrown, preventing resource leaks and ensuring predictable behavior. This update also streamlines the integration with the Failsafe library's asynchronous execution model.

Highlights

• Async Timeout Fix: Addressed a limitation in AsyncExecution that prevented asynchronous tasks from being canceled properly during timeouts, ensuring reliable termination of long-running operations.
• Interrupt Propagation: Modified the execute-get-async macro to correctly propagate InterruptedException and trigger async-cancel! on timed-out futurama futures, preventing resource leaks and ensuring predictable behavior.
• Failsafe API Update: Refactored the asynchronous execution mechanism by switching from FailsafeExecutor.getAsyncExecution with AsyncRunnable to FailsafeExecutor.getAsync with ContextualSupplier, simplifying the internal implementation and aligning with the Failsafe library's recommended approach.
• Version Bump: Updated the project version from 0.2.0 to 0.3.0 in pom.xml and CHANGELOG.md to reflect these significant changes.
• Test Enhancements: Added comprehensive new tests to failsage.core-test to thoroughly verify the timeout policy's ability to enforce time limits and propagate interrupts for both synchronous and asynchronous executions.